Quote:

---

It's not a dependency problem. The problem has to do with Puma being snip, actually

---

LOL!

--------------------
@}--;----- -----;--{@

Edited by Umrahel (08/09/04 07:26 AM)

Post Extras:      

Quote:

---

Uh excuse me but i dont think making personal acttacks against the author of the Mod in question will help to solve the posters problem.

---

I agree. In fact, I'd like to emphasize we don't appreciate any personal attacks to anyone on these forums. Please leave any direct anti-PumaMan (directed to the person) posts out of these forums.

--------------------
I may be lying

Samurai Bunnies

Morrowind Chat



Post Extras:      

Quote:

---

If you want to remove the enitre mod, meshes and textures included, you'd best uninstall GIANTS then re-install Morrowind, incase any key files are missing.

In my case, I removed just the esm and loaded an earlier save without GIANTS. Esms are good for minimising doubling bugs ect, but a real pain to get rid of once you don't want them.

---

Unless the user screws up in the Construction Set and makes the .esp for another mod dependent on the .esm file, an .esm mod shouldn't be any harder (or any easier) than an .esp mod to uninstall.

It's a matter of how much the mod adds to the game world, how cleanly it makes its changes, etc., not whether a mod is an .esm or an .esp.

When removing any mod that adds a lot to the game or makes significant changes to parts of the game, it's probably safer to start over from a save game made before that mod was first installed.

As far as Giants goes:

I tried it for a while a year or so ago. I don't know what kind of installer or uninstaller it uses now, but the installer last year would overwrite existing files without prompting, even if the files it was replacing were newer than the ones included in Giants. I let the installer put the files into an empty directory, then manually installed them, which avoided the problem. (I found out about the overwriting by doing some testing.)

When I decided I wanted to get rid of Giants, I discovered there was no documentation at all for the uninstaller; that was enough to persuade me to ignore the uninstaller and just delete the .esm file (or .esp file? Don't remember now) and the uninstaller, without trying to uninstall the other files.

Post Extras:      

Quote:

---

But yeah I had ENDLESS problems with GIANTS, so I refuse to touch it now >.>

---

Same here, it looks cool, but while running it, I couldnt go anywhere without it saying something was missing and crashing.

then when i uninstalled it it crashed up everything, I had to blow everythying away and start from scratch.

good idea, badly implemented.

Post Extras: